Make MCP stateless when using the HTTP transport#113
Merged
nathanjcochran merged 1 commit intomainfrom Nov 20, 2025
Merged
Conversation
murrayju
approved these changes
Nov 20, 2025
jgpruitt
approved these changes
Nov 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR makes the MCP stateless when using the HTTP transport. See the MCP docs and the StreamableHTTPOptions docs for more info. This change should make Tiger MCP work with a wider range of MCP clients when using the HTTP transport. We weren't doing anything stateful anyways, so there's really no downside.
If we need to do something stateful in the future, or allow for server->client requests, we can re-enable statefulness then.